-
-
Notifications
You must be signed in to change notification settings - Fork 245
feat(i18n): update Chinese (Simplified) translations. #1444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📝 WalkthroughWalkthroughThis pull request updates Chinese locale files (i18n/locales/zh-CN.json and lunaria/files/zh-CN.json). It replaces multiple copy-related strings from "复制" to "拷贝", normalises punctuation (including WCAG punctuation and full-width brackets), adds a new versions/distributions y_axis_label ("下载"), introduces a top-level about.team empty object, and adds a vacations object. All changes are translation/string updates; there are no behavioural code changes. Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
|
Thanks for the PR and detailed rationale! I still prefer sticking with
Happy to discuss more if you have other thoughts! |
|
Personally, I prefer "复制", just like my original translation. To me, it clearly reads as shorthand for "复制到剪贴板" (copy to clipboard). |
i18n/locales/zh-CN.json
Outdated
| }, | ||
| "no_dependency": { | ||
| "label": "(不使用依赖)", | ||
| "label": "(不使用依赖)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated~
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
i18n/locales/zh-CN.json
Outdated
| "i18n": { | ||
| "missing_keys": "{count} 项缺少翻译", | ||
| "copy_keys": "复制键值", | ||
| "copy_keys": "拷贝键值", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reconsider the 复制 → 拷贝 terminology change based on reviewer feedback.
The PR comments from both assigned reviewers (RYGRIT and 9romise) indicate a preference for keeping 复制 rather than switching to 拷贝. Their rationale:
- Browser UIs (Chrome/Edge) use
复制for right-click copy actions, aligning with how most users access the site. - Mainstream Chinese apps (WeChat, Douyin, Xiaohongshu) and developer communities (B站, Zhihu, 掘金) predominantly use
复制for clipboard operations. - As a cross-platform web application, aligning with common browser/web conventions is more natural than macOS-native terminology.
This change affects 10 instances across the file. Please discuss with the reviewers before proceeding, as they've expressed clear preferences to maintain consistency with established conventions.
Also applies to: 130-131, 153-153, 223-223, 228-228, 247-247, 466-467, 639-639
That's totally valid! My initial reasoning was that since iOS translates "Duplicate" as "复制", the term has become ambiguous on digital platforms 1. Copying to the clipboard for a subsequent action, and 2. Creating an immediate duplicate. Translating "Copy" as "拷贝" effectively resolves this confusion. I’ve unified the translation of 'Copy' to '复制'. |


1. Added
vacationssection2. Punctuation & Key Completion
)and two-em dashes⸺for better CJK typography.pkg.versions.y_axis_label.3. Terminology: Reverting
Copyto拷贝Updated 10 instances of
Copyrelated actions to use拷贝instead of复制.Regarding this point, I previously updated
Copyto拷贝in a prior PR. However, it was reverted back to复制in PR #1108. I believe拷贝is a more appropriate translation forCopythan复制for the following reasons:复制is more synonymous with Duplicate (creating an identical replica).拷贝better represents the action of placing content onto the clipboard for a "Copy and Paste" workflow.拷贝. While复制is common in some Windows-influenced contexts (which is clearly wrong imo 😈), translating "Copy" as拷贝is both accurate and unambiguous.Copy,拷贝is a well-established technical term in Chinese that eliminates ambiguity, maintaining a consistent professional tone throughout the project.cc @danielroe @9romise @KazariEX